Registration notification for mobile device management

ABSTRACT

Notification of registration of a mobile device with femto coverage for firmware content management is provided. An attachment component that administers location of mobile devices or a femto access point (AP) conveys a notification to a network platform that manages firmware content updates when a mobile device for which firmware update is available hands off from wireless macro coverage onto femto coverage through the femto AP. The notification is triggered in response to firmware update notification received by the attachment component, or an update flag received by the femto AP. Upon reception of the notification, to exploit wireline bandwidth, the network platform delivers firmware content(s) update through backhaul link to the femto AP to which the mobile device is registered. Femto APs not provisioned to serve a mobile device can be incentivized to authorize the mobile device for coverage and thus facilitate firmware updates.

CROSS-REFERENCE TO RELATED CASES

This application is a continuation application of, and claims thebenefit of priority to each of, U.S. patent application Ser. No.14/491,579, and filed Sep. 19, 2014, and entitled REGISTRATIONNOTIFICATION FOR MOBILE DEVICE MANAGEMENT, which is a divisionalapplication of U.S. patent application Ser. No. 13/476,528, and filedMay 21, 2012, now issued as U.S. Pat. No. 8,868,696, and entitledREGISTRATION NOTIFICATION FOR MOBILE DEVICE MANAGEMENT, which is acontinuation of U.S. patent application Ser. No. 12/327,498, filed onDec. 3, 2008, now issued as U.S. Pat. No. 8,204,968, entitledREGISTRATION NOTIFICATION FOR MOBILE DEVICE MANAGEMENT. The entiretiesof these applications are hereby incorporated herein by reference.

TECHNICAL FIELD

The subject application relates to wireless communications and, moreparticularly, to notification of registration of a mobile device withinfemto coverage area for device content management.

BACKGROUND

In wireless telecommunication, access to radiofrequency (RF) bands isregulated and largely bureaucratic. Even in instances in which a RF bandcan be utilized for wireless operation without a license, like the 2.4GHz Industrial, Scientific and Medical band, frequency resources remainlimited while demand is high. In addition, transmission power for anetwork transmitter is regulated. Accordingly, wirelesstelecommunication development focuses on efficient approaches tomaximize operational and commercial utility, e.g., maximize a number ofserved subscribers through finite resources, without deterioratingsubscriber perceived quality of service, while collecting revenue viadelivery of billable content traffic. A ubiquitous approach toincreasing utility is to mitigate traffic and signaling overhead on theair-interface in order to increase network capacity.

Among traffic overhead is transmission of firmware over-the-air (FOTA)updates, whether critical updates or non-urgent business-as-usual (BAU)updates, which typically are necessary for maintenance and improvementof wireless device performance. It should be appreciated that FOTAupdates can incur substantial signaling since large updates can demandsignificant retry cycles depending on radio link conditions. Moreover,delivery on a wireless link of large FOTA updates can displaysubstantive failure rate, with the ensuing need to resend the update.Furthermore, FOTA updated can be slow since such traffic generally isnon-billable and typically is scheduled limited radio resources. Furtheryet, to compound issues related to communication of FOTA updates, largeservice providers or network operators often manage FOTA updates for asubstantive number (e.g., 10⁵-10⁹) of devices, thus incurringsignificant undesired overhead on the service provider's radio resourceswhen updates are implemented. Therefore, efficient approaches to mobiledevice management can improve traffic conditions and mitigate radioresources employed for FOTA updates; thus, improving service provideroperation and commercial utilities.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 illustrates a schematic wireless telecommunication environment inwhich telecommunication can exploit features and aspects described inthe subject specification.

FIG. 2 illustrates a block diagram of an example system that deliversfirmware update(s) through a backhaul pipe, which transports traffic andcontrol for a network of femto access points, when a device for whichthe firmware update(s) is available registers with a femto access point,in accordance with aspects described herein.

FIG. 3 is a block diagram of an example system that facilitates deliveryof femto content(s) upgrade through a backhaul link, which serves afemto access point, when a device for which the firmware update(s) isavailable registers with the femto access point in accordance withaspects disclosed herein.

FIG. 4 is a block diagram of an example system that drives inclusion ofa femto access point in a pool of femto access points that facilitatefirmware content(s) updates conveyed through backhaul backbone of afemto network in accordance with aspects described herein.

FIG. 5 illustrates an example embodiment of a femto access point thatfacilitates delivery of firmware update(s) in accordance with aspectsdescribed herein.

FIG. 6 presents a flowchart of an example method for updating firmwarecontent(s) through a femto cell backhaul pipe in accordance with aspectsof the subject application.

FIG. 7 is a flowchart of an example method for engaging femto accesspoints for delivery of firmware content(s) updates for a mobile deviceaccording to aspects described herein.

FIG. 8 is a flowchart of an example method for exchanging signaling thatfacilitates firmware content(s) update for a mobile device according toaspects described herein.

FIG. 9 presents a flowchart of an example method for delivering afirmware content(s) update according to aspects described herein.

DETAILED DESCRIPTION

The subject application is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding of the present invention. It may be evident, however, thatthe present invention may be practiced without these specific details.In other instances, well-known structures and devices are shown in blockdiagram form in order to facilitate describing the present invention.

As used in this application, the terms “component,” “system,”“platform,” “service,” “framework,” “interface,” and the like areintended to refer to a computer-related entity or an entity related toan operational machine with one or more specific functionalities. Theentities disclosed herein can be either hardware, a combination ofhardware and software, software, or software in execution. For example,a component may be, but is not limited to being, a process running on aprocessor, a processor, an object, an executable, a thread of execution,a program, and/or a computer. By way of illustration, both anapplication running on a server and the server can be a component. Oneor more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. Also, these components canexecute from various computer readable media having various datastructures stored thereon. The components may communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal).

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Moreover, terms like “user equipment,” “mobile station,” “mobile,”“subscriber station,” “access terminal,” “terminal,” “handset,” andsimilar terminology, refer to a wireless device utilized by a subscriberor user of a wireless communication service to receive or convey data,control, voice, video, sound, gaming, or substantially any data-streamor signaling-stream. The foregoing terms are utilized interchangeably inthe subject specification and related drawings. Likewise, the terms“access point,” “base station,” “Node B,” “evolved Node B,” “home Node B(HNB),” and the like, are utilized interchangeably in the subjectapplication, and refer to a wireless network component or appliance thatserves and receives data, control, voice, video, sound, gaming, orsubstantially any data-stream or signaling-stream from a set ofsubscriber stations. Data and signaling streams can be packetized orframe-based flows.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“agent,” and the like are employed interchangeably throughout thesubject specification, unless context warrants particular distinction(s)among the terms. It should be appreciated that such terms can refer tohuman entities or automated components supported through artificialintelligence (e.g., a capacity to make inferences based on complexmathematical formalisms) which can provide simulated vision, soundrecognition, and so forth.

The subject application provides system(s) and method(s) fornotification of registration of a mobile device within femto coveragearea for device content management. Content can be firmware associatedwith functionalities of the mobile device. In an aspect of the subjectapplication, non-urgent business-as-usual BAU firmware content updatesare suited to be managed as described herein. It is noted that othernon-critical content such as multimedia (e.g., video and sound) contentcan be delivered in accordance with aspects of the subject application.In an aspect of the subject application, a notification is conveyed to anetwork component or platform that manages firmware content(s) updateswhen a mobile device for which an update is available, hands off fromwireless macro network coverage onto a femto cell coverage. Thenotification is delivered in response to a firmware update notificationdelivered to a component that administers location of the mobile device,or an update flag delivered to a femto access point that can providefemto coverage to the mobile device. Upon reception of the notification,to take advantage of the wireline network bandwidth over the wirelessmacro coverage counterpart, the network component or platform thatmanages firmware updates delivers firmware content(s) update throughbackhaul link to a femto access point to which the intended mobiledevice is registered.

In an aspect, when a new non-urgent BAU firmware update required for amobile device becomes available, a mobile device management platformidentifies whether the mobile device can attain femto access coverage,e.g., through data inspection or extraction form a subscriber databaseor provisioning database. When the device is authorized to access afemto access point either provisioned to a subscriber linked to themobile device, or allowed access as a part of a network of firmwareupdate femto access points, an attachment component that can managemacro-to-femto handover conveys a notification to the mobile devicemanagement platform when the mobile device registers with an authorizedfemto access point. The notification triggers delivery of a firmwareupdate to the femto cell that provides coverage to the mobile device.Alternatively, or in addition, when the attachment component determinesthe device is not covered through a femto cell, but rather via macrocoverage, the firmware update is delayed.

To increase a number of provisioned femto access points that canfacilitate coverage to a mobile device, and firmware content(s) updatesrelated therewith, a MDM component can identify a set of femto APswithin a location pattern of the mobile device, and prompt subscribersto whom respective femto APs are provisioned to authorize access tofemto coverage in the respective femto APs. Resources to effect firmwarecontent(s) updates are negotiated and configured with femto APs thatindicate a subscriber has opted in. To drive inclusion, subscribers thatopt in are provided with monetized incentives.

It is noted that the various aspects or features described in thesubject specification can be exploited in substantially any, or any,wireless technology such second generation (2G) technology; e.g., GlobalSystem for Mobile Communications (GSM), or advanced second generation(2.5G) telecommunication technology, e.g., Enhanced Data Rate for GSMEvolution (EDGE); third generation technology (3G) like Third GenerationPartnership Project (3GPP) Universal Mobile Telecommunication System(UMTS), 3GPP Long Term Evolution (LTE), Wideband Code Division MultipleAccess (W-CDMA), or Ultra-broadband Mobility (UMB); advanced 3G such asWorldwide Interoperability for Microwave Access (WiMax); or fourthgeneration (4G) technology such as for example Long Term Evolution (LTE)Advanced

Referring to the drawings, FIG. 1 illustrates a wireless environmentthat includes macro cells and femto cells for wireless coverage inaccordance with aspects described herein. In wireless environment 100,two areas 105 represent “macro” cell coverage, each macro cell is servedby a base station 110. It should be appreciated that macro cells 105 areillustrated as hexagons; however, macro cells can adopt other geometriesgenerally dictated by the deployment or floor plan, geographic areas tobe covered (e.g., a metropolitan statistical area (MSA) or ruralstatistical area (RSA)), and so on. Macro coverage is generally intendedto serve mobile wireless devices, like UE 120 _(A), in outdoorslocations. An over-the-air wireless link 115 provides such coverage, thewireless link 115 comprises a downlink (DL) and an uplink (UL), andutilizes a predetermined band of the radio frequency (RF) spectrum. Asan example, UE 120 _(A) can be a Third Generation Partnership Project(3GPP) Universal Mobile Telecommunication System (UMTS) mobile phone. Itis noted that a base station, its associated electronics, circuitry orcomponents, and a wireless link operated in accordance to the basestation form a radio access network (RAN). In addition, base station 110communicates via backhaul link(s) 151 with a macro network platform 108,which in cellular wireless technologies (e.g., 3rd GenerationPartnership Project (3GPP) Universal Mobile Telecommunication System(UMTS), Global System for Mobile Communication (GSM)) represents a corenetwork. In an aspect, macro network platform 108 controls a set of basestations 110 that serve either respective cells or a number of sectorswithin such cells. Macro network platform 108 also communicates withother base stations (not shown) that serve other cells (not shown).Backhaul link(s) 151 can include a wired backbone link (e.g., opticalfiber backbone, twisted-pair line, T1/E1 phone line, a digitalsubscriber line (DSL) either synchronous or asynchronous, an asymmetricADSL, or a coaxial cable . . . ). Backhaul pipe(s) 155 link disparatebase stations 110.

In wireless environment 100, within one or more macro coverage cell 105,a set of femto cell 125 served by respective femto access points (APs)130 can be deployed. While in illustrative wireless environment 100three femto cells are deployed per macro cell, aspects of the subjectapplication are geared to femto cell deployments with substantive femtoAP density, e.g., 10⁴-10⁸ femto APs 130 per base stations 110. A femtocell 125 typically covers an area that includes confined area 145, whichis determined, at least in part, by transmission power allocated tofemto AP 130, path loss, shadowing, and so forth. While coverage area125 and confined area 145 typically coincide, it should be appreciatedthat in certain deployment scenarios, coverage area 125 can include anoutdoor portion (e.g., a parking lot, a patio deck, a recreation areasuch as a swimming pool and nearby space) while area 145 spans anenclosed living space. Coverage area typically is spanned by a coverageradius that ranges from 20 to 100 meters. Confined coverage area 145 isgenerally associated with an indoor space such as a building, eitherresidential (e.g., a house, a condominium, an apartment complex) orbusiness (e.g., a library, a hospital, a retail store), which encompassa setting that can span about 5000 sq. ft.

A femto AP 130 typically serves a few (for example, 1-5) wirelessdevices (e.g., subscriber station 120 _(B)) within confined coveragearea 125 via a wireless link 135 which encompasses a downlink and anuplink. A femto network platform 109 can control such service, inaddition to mobility handover from macro-to-femto handover and viceversa, and registration and provisioning of femto APs. Control, ormanagement, is facilitated by backhaul link(s) 153 that connect deployedfemto APs 130 with femto network platform 109. Backhaul pipe(s) 153 aresubstantially the same as backhaul link(s) 151. In an aspect of thesubject application, part of the control effected by femto AP 130measurements of radio link conditions and other performance metrics.Femto network platform 109 also includes components, e.g., nodes,gateways, and interfaces, that facilitates packet-switched (PS) (e.g.,internet protocol (IP)) traffic and signaling generation for networkedtelecommunication. It should be appreciated that femto network platform109 can be femto AP 130 can integrate seamlessly with substantially anypacket switched (PS)-based and circuit switched (CS)-based network suchas macro network platform 108. Thus, operation with a wireless devicesuch as 120 _(A) is substantially straightforward and seamless whenhandover from femto-to-macro, or vice versa, takes place. As an example,femto AP 130 can integrate into an existing 3GPP Core Network viaconventional interfaces, or reference links, like Iu-CS, Iu-PS, Gi, Gn.

It is to be noted that substantially all voice or data active sessionsassociated with subscribers within femto cell coverage (e.g., area 125)are terminated once the femto AP 130 is shut down; in case of datasessions, data can be recovered at least in part through a buffer (e.g.,a memory) associated with a femto gateway at the femto network platform.Coverage of a suspended or hotlined subscriber station or associatedaccount can be blocked over the air-interface. However, if a suspendedor hotlined customer who owns a femto AP 130 is in Hotline/Suspendstatus, there is no substantive impact to the customers covered throughthe subject femto AP 130. In another aspect, femto AP 130 can exploithigh-speed downlink packet access either via an interface with macronetwork platform 108 or through femto network platform 109 in order toaccomplish substantive bitrates.

In addition, in yet another aspect, femto AP 130 has a LAC (locationarea code) and RAC (routing area code) that is different from theunderlying macro network. These LAC and RAC are used to identifysubscriber station location for a variety of reasons, most notably todirect incoming voice and data traffic to appropriate pagingtransmitters, and emergency calls as well. As a subscriber station(e.g., UE 120 _(A)) that exploits macro coverage (e.g., cell 105) entersfemto coverage (e.g., area 125), the subscriber station (e.g., UE 120_(A)) attempts to attach to the femto AP 130 through transmission andreception of attachment signaling. The signaling is effected via DL/UL135; in an aspect of the subject application, the attachment signalingcan include a Location Area Update (LAU) and/or Routing Area Update(RAU). Attachment attempts are a part of procedures to ensure mobility,so voice calls and data sessions can continue even after amacro-to-femto transition or vice versa. It is to be noted that UE 120_(A) can be employed seamlessly after either of the foregoingtransitions. In addition, femto networks typically are designed to servestationary or slow-moving traffic with reduced signaling loads comparedto macro networks. A femto service provider (e.g., an entity thatcommercializes, deploys, or utilizes femto access point 130) istherefore inclined to minimize unnecessary LAU/RAU signaling activity atsubstantially any opportunity to do so, and through substantially anyavailable means. It is to be noted that substantially any mitigation ofunnecessary attachment signaling/control is advantageous for femto celloperation. Conversely, if not successful, UE 120 _(A) is generallycommanded (through a variety of communication means) to select anotherLAC/RAC or enter “emergency calls only” mode. It is to be appreciatedthat this attempt and handling process can occupy significant UEbattery, and femto AP capacity and signaling resources (e.g.,communication of pilot sequences) as well.

When an attachment attempt is successful, UE 120 _(A) is allowed onfemto cell 125, and incoming voice and data traffic are paged and routedto the subscriber through the femto AP 130. To facilitate voice and datarouting, and control signaling as well, successful attachment can berecorded in a memory register, e.g., a Visited Location Register (VLR),or substantially any data structure stored in a network memory. It is tobe noted also that packet communication (e.g., voice and data traffic,and signaling) typically paged/routed through a backhaul broadband wirednetwork backbone 140 (e.g., optical fiber backbone, twisted-pair line,T1/E1 phone line, digital subscriber line (DSL) either synchronous orasynchronous, an asymmetric DSL, a coaxial cable . . . ). To this end,femto AP 130 is typically connected to the broadband backhaul networkbackbone 140 via a broadband modem (not shown). In an aspect of thesubject application, femto AP 130 can display status indicators forpower, active broadband/DSL connection, gateway connection, and genericor specific malfunction. In another aspect, no landline is necessary forfemto AP 130 operation.

FIG. 2 illustrates a block diagram of an example system 200 thatdelivers firmware update(s) through a backhaul pipe, which transportstraffic and control for a network of femto access points, when a devicefor which the firmware update(s) is available registers with a femtoaccess point.

Example system 200 includes a mobile device manager (MDM) platform 210that can provide data services (e.g., applications), which can beexecuted via a wireless application protocol (WAP), and facilitateadministration of mobile device(s). Such administration can includefirmware updates for both critical and BAU updates. Firmware updates arebased at least in part on available update content(s) which can beretained in an update content(s) store 259. For example, with respect tocritical updates, content(s) can include security patches; serviceactivation scripts, for example, for activation of services such asvoice, voice and data, or data, which can include internet protocol (IP)television, video-streaming and sound-streaming, online gaming,on-the-cloud data storage; etc. In connection with BAU updates, updatecontent(s) can include drivers for add-on or new mobile'sfunctionalities; patches for adjustment of user equipment operation suchactivation of multi-technology features when a mobile device is capableof operation in various technologies or mode; or the like.

When a firmware content update is available for a device (not shown),MDM platform 210 can exploit a notification component 212 to generate anupdate notification 235 which can prompt a tracking component 214 toaccess a subscriber database 257 to determine whether the device forwhich the update is available can access femto service coverage via oneof more femto access points. In an aspect, the device can access femtocoverage when it is authorized to attach to a femto access point. Suchauthorization can be recorded in an access list (not shown) linked tothe femto access point and retained in subscriber database 257.Information on a device can be received, or uploaded, in subscriberdatabase 257 at a time a femto access point is provisioned and a set ofdevices associated with an account for service through the provisionedfemto AP is authorized to access femto coverage, e.g., to attach orregister with the femto AP; for instance, the devices can belong to thesubscriber responsible for the account or subscribers associated thereofsuch as family members, relatives, friends, coworkers, and so forth.When the device can attain femto coverage, through one or more femtoaccess points, update notification 235 is conveyed to attachmentcomponent 265 and a flag is retained, e.g., in flag(s) table 271, in alocation register 269 to indicate a firmware update is available for thedevice. In an aspect, attachment component can be embodied in a homeagent. Update notification can convey a unique identifier for the device(e.g., a MSISDN, an IMSI, an ESN) and a set of one or more control bitsthat can flag the device for update, and characterize the update. In anaspect, update notification 235 can be embodied in a light-weight file(e.g., a cookie file). Handover component 267 can utilize thenotification flag associated with update indication 235, as anindication or beacon to generate a handover notification 245, orregistration notification, when the device is attached, or registered,with a femto access point. In an aspect, a device can be attached to afemto AP as a result of a successful attachment procedure (e.g., a localarea update (LAU)) effected when the device hands off from macrocellular coverage to femto coverage provided through the femto AP.Attachment component 265, through handover component 267, can convey thegenerated handover notification 245 to mobile device manager platform210, which can deliver firmware update 272 to the femto AP that servesthe device. In an aspect, handover notification 245 can be at least oneof a set of one or more bits, or a light weight file (e.g., a cookiefile), which can facilitate generation of a record of updates providedthrough MDM platform 210.

At least three advantages of delivering firmware update 272 throughbackhaul link 153 are the following. (I) Reduction of network resourcesnecessary to deliver a firmware content(s) update, which typically is anon-billable data transaction. (II) Increased push or download speed forfirmware content(s) update when compared to FOTA update(s) in view ofsubstantive available bandwidth through backhaul backbone of a femtocell network. (III) Improved success rate for firmware content(s)update(s) in view of larger carrier to interference (C/I) ratio inbackhaul link 153 with respect to a radio link.

Alternatively, or in addition, when the device is not attached to afemto access point at a time the update notification 235 is received inattachment component 265, available firmware content(s) update can bedelayed until handover notification 245 is received in MDM platform 210.To determine firmware content(s) are to be delayed, at least twopossible mechanisms can be implemented. (1) MDM platform 210 can triggera timer (e.g., τ) when notification component 212 delivers updatenotification 235, if the timer expires prior to reception of a handovernotification 245, firmware content(s) update that is BAU update can bedelayed until the handover notification 245 is received. (2) Attachmentcomponent 265 can deliver a logic NULL handover notification 245 toindicate that the device for which the firmware update is intended isnot attached to a femto access point. Thus, the logic NULL notificationindicates firmware content is to be delayed; the delay in effect until anon-NULL handover notification 245 is received by notification component212.

To deliver a firmware update in response to a received non-NULL handoverindication 245, MDM platform 210 can convey firmware update 272 togateway node(s) 229 which relays the firmware update 272 to servingnode(s) 227 for communication thereof to the femto access point throughbackhaul pipe 153. As an example, when example system 200 is exploitedin a third generation partnership project (3GPP) Universal MobileTelecommunication Services (UMTS) network, gateway node(s) 229 can beembodied in gateway general packet radio service (GPRS) support node(s)(GGSN), while serving node(s) 227 can be embodied in serving GPRSsupport node(s) (SGSN). In addition, access nodes platform 225 caninclude a tunnel interface (not shown; e.g., a tunnel terminationgateway (TTG) in 3GPP UMTS network(s)) which can facilitate packetizedcommunication with disparate wireless network(s) through gateway node(s)229. In a 3GPP UMTS network(s), gateway node(s) (e.g., GGSN) and tunnelinterface (e.g., TTG) comprise a packet data gateway (PDG). It is notedthat communication among serving node(s) 227 and gateway node(s) 229 canbe facilitated by a reference link (e.g., Gn in EDGE or 3GPP UMTS). Itshould be appreciated that gateway node(s) 229 and serving node(s) 227can be part of access node(s) platform 225, which can include accessnode(s) associated with a macro network platform (e.g., core network) orfemto network platform.

When a firmware update 272 is pushed to a femto access point that servesthe intended wireless device, MDM platform 210 can receive signaling 274from the femto access point (not shown) that indicates whether theupdate was received successfully or it failed. Signaling 272 can beconveyed in a control channel as a set of reserved bits in a frame, or aset of bits in a packet header. When received signaling 274 indicatesfirmware update has been pushed successfully, flags in location register269 are released; e.g., notification component can indicate such releasethrough a disparate update notification 235. Conversely, when signaling274 indicates firmware update 272 is erroneously pushed, MDM platform210 can implement a retry cycle of Q attempts (where Q is a naturalnumber). Magnitude of Q can be configured by a network operatoradministrator.

It is noted that example system 200 can include a processor (not shown)which can confer, at least in part, the described functionality(ies) ofMDM platform 210 and components therein, and attachment component 265and components therein, and substantially any, or any, othercomponent(s) or node(s) included is system 200 or functionally connectedthereto. In an aspect, the processor (not shown) can execute codeinstructions stored in a memory, e.g., memory 225, or memory elementthereon, to provide such described functionality(ies).

FIG. 3 is a block diagram of an example system that facilitates deliveryof femto content(s) upgrade through a backhaul link, which serves afemto access point, when a device for which the firmware update(s) isavailable registers with the femto access point. It should beappreciated that components in example system 400 with like numerals tothose in example system 300 have substantially the same, or the same,functionality.

In example system 300, a mobile network platform 305 (e.g., a CoreNetwork in cellular wireless technologies) includes MDM platform 210that includes notification component 212 and a tracking component 214.In an aspect, when a firmware content(s) upgrade is available for amobile device (e.g., UE 120 _(A)), tracking component 214 can identify aset of femto access points that can serve the mobile device within afemto coverage area (e.g., area 125). To at least that end, as discussedabove, tracking component can access subscriber database 257 and extractand analyze provisioning information and configured access lists thatreveal femto APs that can provide service coverage to the mobile device.Notification component 212 can convey an update flag 308 to one or moreof the femto APs in the set of identified femto APs. Update flag 308 canbe embodied in P-bit word (with P a natural number), or a lightweightfile (e.g., a cookie file), and can be retained within a memory in therecipient femto AP (e.g., femto AP 130). When the mobile (e.g., UE 120_(A)) registers with a femto access point (e.g., femto AP 130) that hasreceived an update flag 308 associated with an available firmwarecontent(s) upgrade for the mobile device, a registration notification312 is received, via backhaul link 153, from the femto AP (e.g., femtoAP 130). When MDM network platform 210 receives registrationnotification 312, it pushes firmware update 314 to the femto AP thatretains the update flag 308; the registration notification 312 isreceived through access node(s) 225. In an aspect, subsequent to afirmware update push, notification 312 can convey an indication whetherthe firmware content(s) update completed successfully or errorsoccurred. Such indication can be a set of bits communicated in a controlchannel, or reserved bits in packet header.

As discussed above, firmware content(s) updates can be delayed until MDMplatform 210 receives registration notification 312 as a result ofmobile device (e.g., UE 120 _(A)) handover from macro cell to femto cellserved through femto AP 130. To determine firmware content(s) are to bedelayed, MDM platform 210 can also can employ the at least two possiblemechanisms described above; namely: (i) MDM platform 210 can trigger atimer (e.g., τ′) when notification component 212 delivers update flag308, if the timer expires prior to reception of a registrationnotification 245, firmware content(s) update, which is a BAU update, canbe delayed until the handover notification 245 is received. (ii) Femtoaccess point (e.g., femto AP 130) can deliver a logic NULL registrationnotification 312 to indicate that the device for which the firmwareupdate is intended is not attached to the femto AP. Thus, the logic NULLnotification indicates firmware content is to be delayed; the delay ineffect until a non-NULL handover notification 245 is received bynotification component 212.

It is noted that in example system 300, mobile network platform 305includes processor 325 which is configured to confer, and can confer, atleast in part, the described functionality(ies) of MDM platform 210 andcomponents therein, and attachment component 265 and components therein,and substantially any, or any, other component(s) or node(s) like accessnode(s) platform 225 included is system 300 or functionally connectedthereto as well. In an aspect, processor 325 can execute codeinstructions stored in a memory, e.g., memory 225, or memory element(s)thereon, to provide such described functionality(ies).

FIG. 4 is a block diagram of an example system 400 that drives inclusionof a femto access point in a pool of femto access points that facilitatefirmware content(s) updates conveyed through backhaul backbone of afemto network in accordance with aspects described herein. It should beappreciated that components in example system 400 with like numerals tothose in example system 300 have substantially the same, or the same,functionality. To drive inclusion of subscribers with associatedprovisioned femto access point(s), such subscribers are incentivized ormotivated to authorize wireless devices, linked to disparate networkprovider consumers, to access femto service coverage through theprovisioned femto access point(s). It should be appreciated thatincluded subscribers and respective femto APs are third-party auxiliaryfemto cells that facilitate implementation of firmware content updates.In an aspect, third-party femto hubs can implemented or pursued forselected service provider consumers, like premium consumers, consumerswith good payment history, non-hotlined consumers, business consumers,or consumers within a predetermined subscriber segment.

It is noted that because firmware content updates are non-billable datatransactions directed to maintaining or improving functionality ofserved mobile devices, a service provider that operates mobile networkplatform 205 generally has an interest in delivering firmware contentupdates reliably while minimizing utilized network resources. Toincentivize a subscriber, authorization to access femto access point(s),and successfully downloaded firmware content(s) updates, are monetizedvia various incentives such as a credit for voice communication minutesor data buckets; add-on applications like extra challenge levels in agame, or features in a calendar application; free licensed multimediasuch as video clips or songs, or coupons for access thereof; discountedrates for international calls for a predetermined period of time ornumber of calls; free-of-charge on-the-cloud storage service for apredetermined period of time; discounts on purchases of mobile devices;or the like. An incentive component 415 can generate and administervarious mechanisms to accrue incentives in exchange for successfullydownloaded firmware update 444 to a femto access point. As an example,downloaded volume of data that is part of a firmware update can beexchanged into a currency or point system internal to mobile networkplatform 205, and incentives can be credited accordingly. As anotherexample, a flat-rate of accrued points per successful firmware updatecan be awarded to a subscriber. In an aspect, credits for incentives canbe retained in incentive(s) store 425, and one or more subscribers thatfacilitate firmware update(s) through one or more femto access pointsassociated therewith can redeem incentive(s) with a service operatorthat administers mobile network platform 205. Alternatively, or inaddition, incentive(s) 446 can be delivered via backhaul pipe 153subsequent to a set of one or more successful firmware update(s) 444.Incentive component also can mitigate fraud, evaluating receivednotifications (e.g., notification 442) to prevent delivery ofincentive(s) upon counterfeit notifications.

In an aspect, to select one or more femto access points to serve asupdate hubs in exchange of monetized incentives, intelligent component405 can establish a location pattern for a mobile device (e.g., UE 120_(A)) linked to a subscriber. A location pattern can be determinedthrough analysis of historic attachment data which can be retained inlocation register 269; intelligent component 405 can conduct theanalysis. In an aspect, intelligent component 405 employs historicattachment data to reason or draw conclusions about, e.g., infer alocation pattern. Intelligent component 405 can infer a location patternbased at least in part on artificial intelligence, or machine learning,techniques, which apply advanced mathematical algorithms—e.g., decisiontrees, neural networks, regression analysis, principal componentanalysis (PCA) for feature and pattern extraction, cluster analysis,genetic algorithm, tabu search, and reinforced learning—to collectedattachment information.

In particular, intelligent component 410 can employ at least one ofnumerous methodologies for learning from data and then drawinginferences from the models so constructed, e.g., Hidden Markov Models(HMMs) and related prototypical dependency models, more generalprobabilistic graphical models, such as Dempster-Shafer networks andBayesian networks, e.g., created by structure search using a Bayesianmodel score or approximation, linear classifiers, such as support vectormachines (SVMs), non-linear classifiers, such as methods referred to as“neural network” methodologies, fuzzy logic methodologies, and otherapproaches that perform data fusion, etc.) in accordance withimplementing various automated aspects described herein.

With a location pattern for a mobile device, and based at least in parton deployment configuration (e.g., a floor plan) of femto cells,intelligent component 405 can identify a set of femto access pointswithin the location pattern, and extract information for a set ofsubscribers that are provisioned to utilize the identified set of femtoaccess points. Each subscriber in the set of subscribers can beprompted, e.g., through signaling 434, to opt in to authorize the mobiledevice (e.g., UE 120 _(A)) to access a respective femto access pointassociated with the prompted subscriber. For a subscriber that opts into receive incentives in exchange for allowing the mobile device to campin one or more femto access points associated with the subscriber, MDMplatform 210 can configure, via signaling 434, the one or more femtoaccess points to establish privacy settings, or available femto APresources (e.g., memory space to retain firmware update 144; bandwidth;quality of service; time interval(s) the mobile device is authorized tocamp in the femto AP . . . ) directed to firmware update 144 for themobile device. Such configuration can be negotiated among the one ormore femto APs and mobile network platform 205; negotiated configurationcan be effected, at least in part, through MDM platform 210.

To promote privacy of subscriber that provides femto AP for firmwareupdate 144, mobile network platform 205, through handover component 267,can allow a mobile device for which a firmware update is available toreceive traffic in the femto DL (e.g., DL element of link 135) but notto communicate in the UL (UL element of link 135) except for emergencycalls. It should be appreciate that such asymmetric configuration alsocan ensure, at least in part, privacy of the device since UL traffic ismitigated.

It should be appreciated that firmware update 444 can be conductedpartially in each femto access point that is configured to facilitatesuch firmware update: Notification 442 can trigger firmware update 444when a mobile device attaches to a femto AP, when femto AP detaches fromthe femto AP, notification 442 can indicate firmware update 44 is to behalted. Firmware update 444 resumes when the a notification 442 isreceived as a result the mobile device attached to a disparate femto APthat has previously received an update flag 438. Mobile network platform305 includes processor 325 which is configured to confer, and canconfer, at least in part, the described functionality(ies) of MDMplatform 210 and components therein, and attachment component 265 andcomponents therein, and substantially any, or any, other component(s) ornode(s), like access node(s) platform 225, included or functionallyconnected thereto as well. In an aspect, processor 325 can execute codeinstructions stored in a memory, e.g., memory 255, or memory element(s)thereon, to provide such described functionality(ies).

FIG. 5 illustrates an example embodiment 500 of a femto access pointthat facilitates delivery of firmware update(s) in accordance withaspects described herein. In example embodiment 500, femto AP 502 canreceive and transmit signal(s) (e.g., attachment signaling) from and towireless devices like femto access points, access terminals, wirelessports and routers, or the like, through a set of antennas 510 ₁-510 _(N)(N is a positive integer). It should be appreciated that antennas 510₁-510 _(N) are a part of communication platform 505, which compriseselectronic components and associated circuitry that provides forprocessing and manipulation of received signal(s) and signal(s) to betransmitted. In an aspect, communication platform 505 includes areceiver/transmitter 506 that can convert signal (e.g., signaling 274)from analog to digital upon reception, and from digital to analog upontransmission. In addition, receiver/transmitter 506 can divide a singledata stream into multiple, parallel data streams, or perform thereciprocal operation. Coupled to receiver/transmitter 506 is amultiplexer/demultiplexer 507 that facilitates manipulation of signal intime and frequency space. Electronic component 507 can multiplexinformation (data/traffic and control/signaling) according to variousmultiplexing schemes such as time division multiplexing (TDM), frequencydivision multiplexing (FDM), orthogonal frequency division multiplexing(OFDM), code division multiplexing (CDM), space division multiplexing(SDM). In addition, mux/demux component 507 can scramble and spreadinformation (e.g., codes) according to substantially any code known inthe art; e.g., Hadamard-Walsh codes, Baker codes, Kasami codes,polyphase codes, and so on. A modulator/demodulator 508 is also a partof communication platform 505, and can modulate information according tomultiple modulation techniques, such as frequency modulation, amplitudemodulation (e.g., M-ary quadrature amplitude modulation (QAM), with M apositive integer), phase-shift keying (PSK), and the like.

In an aspect, femto access point 502 includes a notification component515 that can convey an indication, e.g., notification 572, when a mobiledevice flagged for firmware content(s) update registers with femto AP502. Records of flagged mobile devices that can be provided femtocoverage through femto AP 502 can be retained in memory element updateflag(s) 549 within memory 545. In an aspect, update flag(s) 549 caninclude a unique mobile device identifier, and information related tothe available firmware update.

Additionally, femto AP 502 includes display interface 535, which candisplay functions that control functionality of femto AP 805, or revealoperation conditions thereof; e.g., light-emitting-diode (LED)indicator(s) that convey available firmware content update(s) areavailable for download. In addition, display interface 812 can include ascreen to convey information to an end user; for instance, displayinterface 812 can display a summary of successful firmware updatescarrier out over a predetermined period of time; a message thatindicates received incentives (e.g., incentive(s) 576) or creditedincentives exchanged for successful firmware updates; and so on. In anaspect, display interface 812 can be embodied in a liquid crystaldisplay (LCD), a plasma panel, a monolithic thin-film basedelectrochromic display, etc. Display interface 812 also can facilitatesdata entry (e.g., through a linked keypad or via touch gestures), whichcan facilitate femto AP 802 to receive external commands or responsessuch as input associated with configuration of resources for directed tothird-party firmware content(s) update(s), and updated profile(s) 547associated with such configuration.

Update component 525 can facilitate, at least in part, configuration andenforcement of update profile(s) 547, which can include at least one ofmemory allocated to retain firmware update(s); bandwidth granted forthird-party firmware updates for third-party mobile devices; quality ofservice, such as best effort; time interval(s) third-party mobile deviceis authorized to camp in femto AP 502; a priority ranking for firmwareupdate push for mobile devices authorized to attach, register, or campin femto AP 502, e.g., mobile device linked to owner or leaser of femtoAP 502 are updated before a third-party mobile device is updated; numberof iterations in firmware update retry cycle(s); or the like. In anaspect, for firmware content(s) updates directed to a mobile devicewithin a service account linked to a subscriber to whom the femto AP isprovisioned, firmware updates can be downloaded and cached in femto AP,e.g., in memory 545 to the extent memory is available, until the mobiledevice within the account attaches to the femto AP. At least anadvantage of such update mechanism is to reduce signaling with mobilenetwork platform that operates the femto AP (e.g., femto AP 502).

Additionally, update component 525 can assess whether communicationresources are available to receive a firmware update 574, and reject afirmware update when resources are unavailable; to at least that end,update component can utilize information received available through atleast one of update flag(s) 549 or update profile(s) 547. In addition,update component 525 can push firmware update(s) 272, via communicationplatform 505, and determine whether delivery of an update succeeds orfails; update component 525 can signal, via signaling 564, deliverysuccess or failure. Furthermore, receive update content(s) can beretained in update content(s) store 551 to facilitate implementation ofupdate retry cycle(s). In an aspect, several firmware content(s) updatescan be aggregated as a part of a retry cycle, in case a mobile devicefor which firmware update(s) detaches from femto AP 502 prior to asuccessful delivery of firmware content(s) update.

Femto access point 502 includes a broadband network interface 514 thatfacilitates connection of femto AP 502 to femto network via backhaullink(s) 153, which is included in link 565, which enables incoming andoutgoing data flow from and a mobile network platform (e.g., mobilenetwork platform 305). Broadband network interface 514 can be internal(as illustrated) or external to femto AP 502, and it can utilize, atleast in part, display interface 532 for end-user interaction and statusinformation delivery; e.g., presentation of log records of firmwareupdates carried out through femto AP 502.

In addition, femto access point 502 also includes a processor 555 thatcan confer, at least in part, one or more functionalities describedherein to substantially any, or any, electronic component, platform, orinterface in femto AP 502. In an aspect, processor 555 can execute codeinstructions retained in memory 545 to effect, at least in part, thedescribed functionality(ies) of the various components, platform, orinterfaces, that reside within femto AP 502. Processor 555 isfunctionally connected to various components and interfaces within femtoAP 502 via a bus 545. Processor 555 also is functionally connected tocommunication platform 505 and can facilitate operations on data (e.g.,symbols, bits, or chips) for multiplexing/demultiplexing, such aseffecting direct and inverse fast Fourier transforms, selection ofmodulation rates, selection of data packet formats, inter-packet times,etc.

Memory 545 also can store data structures, code instructions and programmodules, system or device information, code sequences for scrambling,spreading and pilot transmission, femto AP floor plan configuration, andso on. Processor 555 is functionally coupled to the memory 545 in orderto store and retrieve information necessary to operate and/or confer, atleast in part, functionality(ies) described herein to the variouscomponents, platform, and interfaces of femto AP 502.

In view of the example systems described above, example methodologies,or methods, that can be implemented in accordance with the disclosedsubject matter can be better appreciated with reference to flowcharts inFIGS. 6-9. For purposes of simplicity of explanation examplemethodologies, or methods, are presented and described as a series ofacts; however, it is to be understood and appreciated that the claimedsubject matter is not limited by the order of acts, as some acts mayoccur in different orders and/or concurrently with other acts from thatshown and described herein. For example, it should be understood andappreciated that a methodology could alternatively be represented as aseries of interrelated states or events, such as in a state diagram orinteraction diagram. Moreover, not all illustrated acts may be requiredto implement a methodology, or method, in accordance with the subjectspecification. Additionally, two or more methodologies, or methods,described herein can be enacted in conjunction. Furthermore, it shouldbe further appreciated that the methodologies, or methods, disclosedhereinafter and throughout this specification are capable of beingstored on an article of manufacture to facilitate transporting andtransferring such methodologies to computers for execution by aprocessor or for storage in a memory. Further yet, it is noted that aprocessor that confers, at least in part, functionality to one or morecomponents that can enact one or more example methods described hereinalso can effect the acts included therein.

FIG. 6 presents a flowchart of an example method 600 for updatingfirmware content(s) through a femto cell backhaul pipe in accordancewith aspects of the subject application. This example method 600 can beenacted by a component in a wireless network platform (e.g., mobilenetwork platform 305). At act 610, it is determined whether femto cellcoverage is attainable for the device. In an aspect, femto cell coverageis attainable when a consumer linked to the device subscribes for femtocell service for a specific location (e.g., area 125). Suchdetermination can be performed by a tracking component (see, e.g., FIG.2) within the wireless network platform that enacts the method byretrieving information on subscription type(s) for the mobile device asretained in subscriber records in a memory element within the wirelessnetwork platform. It is noted that a subscriber not directly linked tothe device and with access to femto cell service, e.g., the consumer isassociated with a provisioned femto access AP, can authorize the mobiledevice for femto cell coverage through the femto access pointprovisioned to the consumer. At 615 it is checked whether femto cellcoverage, or femto coverage, is attainable. In the negative case, thesubject example method ends. Conversely, at act 620 a notificationfirmware content(s) update for a mobile device is available. In anaspect, the firmware content(s) update is considered business-as-usual(BAU) non-urgent update. In another aspect, as described above, thenotification that firmware content(s) update are available for a mobiledevice can include a unique identifier for the device (e.g., a MSISDN,an IMSI, an ESN), a set of one or more control bits that can flag themobile device for update. In addition, the notification can characterizethe update; e.g., add-on feature; multi-technology compatibility patch;operational script; etc. In another aspect, the notification also can beembodied in a light-weight file (e.g., a cookie file).

At act 630, firmware content(s) update is delayed when the mobile deviceis registered to a femto access point for femto coverage. Registrationreflects the mobile device is attached to a femto cell and recorded in alocation register (e.g., HLR, VLR, TTG) having an updated location(e.g., LAC/RAC) of the mobile device. In an aspect, the mobile devicebecomes registered for femto cell coverage after macro-to-cellularhandover.

At act 640 it is evaluated whether a notification the mobile deviceregistered to a femto access point (e.g., femto AP 130) for femtocoverage is received. In the negative case, flow is directed to act 630,and the update remains delayed. In the affirmative case, availablefirmware content(s) update is pushed through femto cell backhaul pipeassociated with the femto access point at act 650. In an aspect,utilization of backhaul pipe can particularly benefit delivery of large(e.g., firmware content(s) in excess of a MB) updates. It is to be notedthat at least one advantage of employing the backhaul pipe fordelivering firmware content(s) update is that it reduces networkresources in the wireless network spent for such non-billable datatransaction(s), improves update delivery speed, and improve(s) successrates of these types of actions, with the ensuing improvement incustomer experience. At act 660, it is checked whether firmware push wassuccessful. In the affirmative case, firmware content(s) update isconcluded. Conversely, at act 670, it is checked whether a retry cycle,e.g., a cycle of Q attempts, with Q a positive integer, is to beimplemented. In the positive case, flow is directed to 650, whereas inthe negative case, an indication firmware content(s) failed is deliveredto the femto access point.

FIG. 7 is a flowchart of an example method 700 for engaging femto accesspoints for delivery of firmware content(s) updates for a mobile deviceaccording to aspects described herein. In an aspect, the subject examplemethod 700 can be enacted by one or more component(s), operatingindependently or in conjunction, in a wireless network platform (see,e.g., FIG. 4). At act 710 a location pattern is determined for a mobiledevice. Determination is made based upon historic data collected from alocation register (e.g., HLR, VLR) over a predetermined period of time.At act 720, identify a set of femto access points within the locationpattern. In an aspect, the identified femto APs can include femto cellsneighboring a residence of a subscriber linked to a device that is toreceive firmware content(s) update; femto APs deployed within a servicearea such as a bank, a medical doctor's office, or customer servicefield office (e.g., an AT&T store); femto APs in the subscriberworkplace; or femto cell located in alike areas.

At act 730 a subscriber of a femto access point within the set ofidentified femto APs within the location pattern is prompted to opt inas a firmware content(s) update hub in exchange for monetizedincentives. The subscriber can be prompted through a display interfaceof the femto AP, wherein a message can offer the subscriber to elect tofacilitate the femto AP linked therewith for firmware content(s) update.The prompt through the femto AP can exploit various aural and visualindicia. In another aspect, the subscriber can be prompted through a SMScommunication, a MMS communication, an email message, or an instantmessage delivered to a wireless device associated therewith. Incentives(e.g., incentive(s) 576) can include free voice minutes or data buckets,wherein a data bucket, for example, is a unit of data such as 10 MB andcan be utilized for billing reference in data delivery within high-speedtechnologies (e.g., 4G technology); add-on applications or features formobile and non-mobile devices served by the femto AP; licensedmultimedia such as songs, or movies or video snippets; coupons forservice such as free-of-charge roaming minutes and internationalcalling; free on-the-cloud storage service for subscriber data;differentiated rating for a predetermined time interval, configured bythe service provider, for specific services; and so on.

At act 740, the femto access point in the set of femto APs within thelocation pattern is configured to extend coverage to the mobile devicewhen an indication the subscriber associated with the femto AP opts inis received. In an aspect the indication is received through one or moretransport mechanisms, based at least in part on the interface employedfor prompting the subscriber, as described above in connection with act730; for instance, the indication can be a user supplementary servicedata (USSD) code, a SMS communication, a MMS communication, an emailcommunication, etc. Configuration can include at least one of deviceidentifiers for a set of devices authorized to utilize the femto AP,security features to mitigate unauthorized access to content(s) withinfemto AP such as system files, femto AP configuration information, orthe like; quality of service (QoS) to be served through the hub femto APfor firmware content(s) updates; and so on. Configuration of femto APcan proceed in accordance with privacy settings established by thesubscriber that opts in. Additionally, configuration also can includenegotiating resources for firmware updates, wherein the negotiatedresources can include at least one of memory allocated to retainfirmware update(s); bandwidth granted for third-party firmware updatesfor third-party mobile devices; quality of service, such as best effort;time interval(s) third-party mobile device is authorized to camp infemto AP 502; a priority ranking for firmware update push for mobiledevices authorized to attach, register, or camp in femto AP 502, e.g.,mobile device linked to owner or leaser of femto AP 502 are updatedbefore a third-party mobile device is updated; number of iterations infirmware update retry cycle(s).

At act 750, a notification that firmware content(s) update for themobile device is available is conveyed. In an aspect, the notificationcan be a set of one or more bits in a control channel or header of acontrol packet or frame, or a lightweight file (e.g., a cookie file). Atact 760, receive a notification when the mobile device is attached tothe femto access point in the set of femto APs within the locationpattern. At act 770, firmware content(s) update is pushed through thebackhaul link of the femto access point in the set of femto APs withinthe location pattern. At act 780, incentive(s) are awarded to femtoaccess point within the set of femto APs within the location pattern.Award of incentive(s) can include a fraud mitigation act in whichattachment of the mobile device to the femto cell, or femto AP, isconfirmed at the mobile network platform level, for example, to mitigateawarding incentives based upon a rogue notification. In addition, aspart of awarding incentive(s), an indication of awarded incentive(s) canbe conveyed to the femto AP in order for a subscriber linked thereto tobecome aware of the incentive(s). In an aspect, such indication caninclude a directive to display visual or aural indicia in a displayinterface in the femto AP. Indication can be provided at specific times,after incentive(s) have been accumulated, or at the time firmwarecontent(s) has been successfully pushed.

At least one advantage of the subject example method 700 is thattransport and delivery of firmware content(s) update is driven to takeplace through backhaul backbone network, with associated communicationresources.

FIG. 8 is a flowchart of an example method 800 for exchanging signalingthat facilitates firmware content(s) update for a mobile deviceaccording to aspects described herein. The subject example method can beenacted by a network platform component (e.g., attachment component) ornetwork node (e.g., femto AP 130) that can track location andregistration status of a mobile device. At act 810, an update flag(e.g., update flag 568), or notification, that firmware content(s)update is available for a mobile device is received. In an aspect, thenotification is received by a femto cell access point and can beretained therein. At act 820, a notification is conveyed when the mobiledevice is registered, or attached, to an access point that serves afemto cell. In an aspect, the notification is embodied in one of a setof K bits (K is a natural number) or a lightweight file (e.g., a cookiefile). At act 830, the firmware content(s) update available for themobile device is received. At act 840, the available firmware content(s)update is delivered to the mobile device.

FIG. 9 presents a flowchart of an example method 900 for delivering areceived firmware content(s) update according to aspects describedherein. This example method 900 can be enacted by a femto access point(e.g., femto AP 130), or one or more component therein, e.g., updatecomponent 525. At act 910, it is evaluated whether resources areavailable to receive firmware content(s) update. Resources can includeat least one of memory, either internal or external or both, backhaullink bandwidth. When resources are not available, or sufficient,firmware content update(s) are rejected at act 920. Conversely, firmwarecontent(s) updates directed to a set of mobile device is received at act930; the set of mobile devices include one or more mobile devices. In anaspect, act 910 can occur after firmware update is received. At act 940,firmware content(s) update is delivered to an intended registered mobiledevice. The mobile device is registered to the femto access point thatreceives the update and provides femto service. At act 950, one ofupdate success or update failure is signaled. Signal can be embodied inan K-bit work (K is a natural number).

Various aspects or features described herein may be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques. It is noted that method implementationsof aspects of the specification described herein can be effected througha processor, or program modules or code instructions stored in a memorythat are executed by a processor, or other combination of hardware andsoftware, or hardware and firmware. The term “article of manufacture” asused herein is intended to encompass a computer program accessible fromany computer-readable device, carrier, or media. For example, computerreadable media can include but are not limited to magnetic storagedevices (e.g., hard disk, floppy disk, magnetic strips . . . ), opticaldisks (e.g., compact disc (CD), digital versatile disc (DVD), Blu-raydisc (BD) . . . ), smart cards, and flash memory devices (e.g., card,stick, key drive . . . ).

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor may also be implemented as acombination of computing processing units.

In the subject specification, terms such as “store,” “storage,” “datastore,” “data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. For example, informationrelevant to operation of various components described in the disclosedsubject matter, and that can be stored in a memory, can comprise, but isnot limited to comprising, subscriber information; femto cellconfiguration (e.g., devices served by a femto AP) or service policiesand specifications; privacy policies; add-on features, and so forth. Itwill be appreciated that the memory components described herein can beeither volatile memory or nonvolatile memory, or can include bothvolatile and nonvolatile memory.

By way of illustration, and not limitation, nonvolatile memory caninclude read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable ROM (EEPROM), or flashmemory. Volatile memory can include random access memory (RAM), whichacts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), anddirect Rambus RAM (DRRAM). Additionally, the disclosed memory componentsof systems or methods herein are intended to comprise, without beinglimited to comprising, these and any other suitable types of memory.

What has been described above includes examples of systems and methodsthat provide advantages of one or more embodiments of the subjectapplication. It is, of course, not possible to describe everyconceivable combination of components or methodologies for purposes ofdescribing the subject application, but one of ordinary skill in the artmay recognize that many further combinations and permutations of theclaimed subject matter are possible. Furthermore, to the extent that theterms “includes,” “has,” “possesses,” and the like are used in thedetailed description, claims, appendices and drawings such terms areintended to be inclusive in a manner similar to the term “comprising” as“comprising” is interpreted when employed as a transitional word in aclaim.

What is claimed is:
 1. A method, comprising: sending, by a network device comprising a processor to a femto cell device of a femto network, an update flag associated with an availability of a firmware update for a mobile device of the femto network; in response to a first indication that the mobile device is not registered with the femto cell device, delaying, by the network device, sending of the firmware update; sending, by the network device, data representing a data storage incentive to the femto cell device to transfer a connection of the mobile device from a base station device of a wireless network to the femto cell device to receive the firmware update; in response to a second indication that the mobile device has registered with the femto cell device, receiving, by the network device, a registration notification, via a backhaul link, from the femto cell device; based on the second indication, sending, by the network device, the firmware update to the femto cell device; in response to the sending the firmware update, receiving, by the network device, error bits indicative of an error associated with the firmware update at the femto cell device being determined to have been unsuccessful, wherein the error bits are received via a control channel between the femto cell device and the network device; and in response to the receiving the error bits, initiating, by the network device, a retry cycle to resend the firmware update to the femto cell device.
 2. The method of claim 1, further comprising: determining, by the network device, whether a resource of the mobile device is available to receive the firmware update.
 3. The method of claim 2, wherein the resource comprises a memory to store the firmware update.
 4. The method of claim 3, further comprising: generating, by the network device, the firmware update based on a condition associated with a quality of service enabled by the resource being determined not to have been satisfied.
 5. The method of claim 3, further comprising: generating, by the network device, the firmware update based on a condition associated with a quality of service enabled by the resource being determined to have been satisfied.
 6. The method of claim 1, further comprising: in response to the mobile device transferring the connection, initiating, by the network device, a delivery of the firmware update to the femto cell device.
 7. The method of claim 6, wherein the initiating the delivery comprises initiating the delivery of signal data representative of a transferred connection between the mobile device and the femto cell device.
 8. A system, comprising: a processor; and a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations, comprising: sending, to a femto cell device of a femto network, flag data that indicates that a firmware content update is available for a mobile device; sending, to the femto cell device, incentive data related to an incentive for the mobile device to register with the femto cell device to receive the firmware content update, wherein the incentive is associated with a data store; in response to a first indication that the mobile device is not registered with the femto cell device, delaying sending of the firmware update; in response to the mobile device being determined to have registered with the femto cell device, receiving a registration notice from the femto cell device; based on the registration notice, sending, to the femto cell device, the firmware content update; in response to the sending the firmware content update, receiving notification data indicative of a notification that the firmware content update at the femto cell device has been determined to have been unsuccessful, wherein the notification data comprises error bits; and in response to the receiving the notification data, resending the firmware update a defined number of times.
 9. The system of claim 8, wherein the mobile device is a first mobile device, and wherein the operations further comprise: based on a bandwidth granted for the firmware content update via a second mobile device, configuring an update profile.
 10. The system of claim 8, wherein the operations further comprise: based on the firmware content update, configuring an update profile.
 11. The system of claim 10, wherein the configuring is based on a priority ranking of the firmware content update.
 12. The system of claim 8, wherein the operations further comprise: in response to determining that a communication resource is unavailable, generating the firmware content update.
 13. The system of claim 8, wherein the operations further comprise: based on a condition associated with wireless device resources being determined not to have been satisfied, resending the firmware content update.
 14. The system of claim 8, wherein the notification is a first notification, and wherein the operations further comprise: receiving a second notification, via a notification component, when the mobile device is attached to the femto cell device.
 15. A non-transitory machine-readable storage medium, comprising executable instructions that, when executed by a processor, facilitate performance of operations, comprising: sending, to a femto cell device of a femto network, update flag data comprising a first indication that a firmware content update is available for a mobile device; sending incentive data, related to an incentive for the mobile device to register with the femto cell device, to the mobile device, wherein the incentive data is associated with a data storage for the mobile device; in response to a second indication that the mobile device has not registered with the femto cell device, receiving a registration notification and delaying sending the firmware content update to the femto cell device; in response to the sending the firmware content update, receiving notification data representative of a notification that installation of the firmware content update at the femto cell device has been determined to be unsuccessful, wherein the notification data comprises an error bit received via a control channel; and based on the installation of the firmware content update being determined to be unsuccessful, resending the firmware content update to the femto cell device a determined number of times.
 16. The non-transitory machine-readable storage medium of claim 15, wherein the operations further comprise: based on a condition associated with a mobile device resource being determined not to have been satisfied, delaying the sending the firmware content update.
 17. The non-transitory machine-readable storage medium of claim 16, wherein the mobile device resource enables a bandwidth associated with the mobile device.
 18. The non-transitory machine-readable storage medium of claim 15, wherein the operations further comprise: tracking a location of the mobile device relative to the femto cell device.
 19. The non-transitory machine-readable storage medium of claim 15, wherein the notification is a first notification, and wherein the operations further comprise: receiving a second notification in response to the mobile device being determined to have been attached to the femto cell device.
 20. The non-transitory machine-readable storage medium of claim 19, wherein the operations further comprise: based on the receiving the second notification, tracking a registration status associated with a registration of the mobile device to the femto cell device. 